GitHub Issue 111: Query metadata editor indicates all fields as "New Field"#1892
Merged
cnathe merged 5 commits intorelease25.11-SNAPSHOTfrom Nov 18, 2025
Merged
GitHub Issue 111: Query metadata editor indicates all fields as "New Field"#1892cnathe merged 5 commits intorelease25.11-SNAPSHOTfrom
cnathe merged 5 commits intorelease25.11-SNAPSHOTfrom
Conversation
…w Field" - use the field.lockExistingField property to determine if field is new or existing
labkey-nicka
approved these changes
Nov 17, 2025
cnathe
added a commit
that referenced
this pull request
Nov 19, 2025
### version 6.70.8
*Released*: 19 November 2025
- Merge from release25.11-SNAPSHOT to develop
- includes changes from 6.68.4 #1892
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
https://github.com/LabKey/internal-issues/issues/111
Related Pull Requests
Changes